• I have read the contributing guideline and understand that I have made the correct modifications

Description

Since v3.2.0, Tandoor Recipes now comes with a pre-configured internal NGINX server. This has the following effect for the proxy configuration:

• The port exposed by default was changed from 8080 to 80.
• Their internal NGINX server now handles the mediafiles by itself, which used to be a manual configuration step in the SWAG config.

This PR reflects these changes in the recipes.subdomain.conf.sample file.

Benefits of this PR and context

At the moment, using the latest version of Tandoor Recipes with the default template leads to a broken configuration.

How Has This Been Tested?

Tested this on my local instance of SWAG.

Source / References

See TandoorRecipes/recipes#3851:

Tandoor 1 includes gunicorn, a python WSGI server that handles python code well but is not meant to serve mediafiles. Thus it has always been recommended to setup an nginx webserver (not just a reverse proxy) in front of Tandoor to handle mediafiles. The gunicorn server by default is exposed on port 8080

Tandoor 2 now bundles nginx inside the container and exposes port 80 where mediafiles are handles by nginx and all the other requests are (mostly) passed to gunicorn.

To update you must simply change your port or reverse proxy configuration to access port 80 instead of port 8080.